Product People & Key Stakeholders
Product People & Key Stakeholders
Last Updated: 2025-10-29 Source: Employment Hero (manual sync) Purpose: Live directory of product-related roles and senior management for RACI matrices, PRDs, and stakeholder communications
How to Update This Document
Use the Employment Hero to refresh this data:
# Export senior managementnode .claude/tools/employmenthero/search-employees.cjs --senior --json > senior-mgmt.json
# Export product teamnode .claude/tools/employmenthero/search-employees.cjs --department "Product" --json > product-team.json
# Export business analystsnode .claude/tools/employmenthero/search-employees.cjs --role "Business Analyst" --json > ba-team.jsonThen use Claude to transform the JSON into this document format.
Senior Management
C-Suite
Chief Executive Officer
- Name: [TBD]
- Email: [TBD]
- Role in Product: Strategic direction, final approvals
Chief Product Officer
- Name: [TBD]
- Email: [TBD]
- Role in Product: Product strategy, roadmap ownership
Chief Technology Officer
- Name: [TBD]
- Email: [TBD]
- Role in Product: Technical feasibility, architecture decisions
Chief Operating Officer
- Name: [TBD]
- Email: [TBD]
- Role in Product: Operational impact, resource allocation
Product Leadership
Head of Product
- Name: [TBD]
- Email: [TBD]
- Reports to: CPO
- Responsibilities: Product vision, team leadership, prioritization
Product Directors
-
Director - Consumer Products
- Name: [TBD]
- Email: [TBD]
- Focus: Consumer journey, participant experience
-
Director - Provider Products
- Name: [TBD]
- Email: [TBD]
- Focus: Provider portal, service delivery
Product Owners
Consumer Journey
- Name: [TBD]
- Email: [TBD]
- Epics: Consumer onboarding, participant portal
- Jira: @[username]
Work Management
- Name: [TBD]
- Email: [TBD]
- Epics: Rostering, scheduling, workforce management
- Jira: @[username]
Invoicing & Billing
- Name: [TBD]
- Email: [TBD]
- Epics: Invoice V2, payment processing, NDIS claiming
- Jira: @[username]
Budgets & Services
- Name: [TBD]
- Email: [TBD]
- Epics: Budget management, service agreements, plan management
- Jira: @[username]
Business Analysts
Senior Business Analyst
- Name: [TBD]
- Email: [TBD]
- Focus: Requirements analysis, stakeholder liaison
- Works with: All product owners
Business Analyst - Technical
- Name: [TBD]
- Email: [TBD]
- Focus: Technical requirements, API integrations, system architecture
Business Analyst - Domain Expert
- Name: [TBD]
- Email: [TBD]
- Focus: NDIS compliance, industry regulations, Support at Home
UX/Product Design
Head of Design
- Name: [TBD]
- Email: [TBD]
- Responsibilities: Design system, accessibility standards (WCAG 2.1 AA)
Product Designers
-
Senior Product Designer
- Name: Bruce Blyth (example)
- Email: [TBD]
- Focus: Consumer-facing products, Figma designs
-
Product Designer - Provider
- Name: [TBD]
- Email: [TBD]
- Focus: Provider portal, worker apps
Engineering Leadership
VP Engineering / Head of Engineering
- Name: [TBD]
- Email: [TBD]
- Role in Product: Technical delivery, capacity planning
Engineering Managers
-
EM - Consumer Products
- Name: [TBD]
- Team: Frontend/Backend devs for consumer journey
-
EM - Provider Products
- Name: [TBD]
- Team: Rostering, work management, mobile apps
-
EM - Platform
- Name: [TBD]
- Team: Core services, integrations, billing
Stakeholder Groups
Compliance & Legal
- Head of Compliance: [TBD]
- Role: NDIS compliance, privacy, data security
- Involvement: All features with regulatory impact
Operations
- Head of Operations: [TBD]
- Role: Operational processes, training, support impact
- Involvement: Features affecting workflows
Customer Success
- Head of Customer Success: [TBD]
- Role: Customer feedback, feature adoption, support tickets
- Involvement: User experience improvements
Finance
- CFO / Head of Finance: [TBD]
- Role: Financial impact, budgeting, pricing
- Involvement: Billing, invoicing, payment features
RACI Quick Reference
When creating RACI matrices, use these typical patterns:
Product Features
- Responsible: Product Owner, Business Analyst
- Accountable: Product Director or Head of Product
- Consulted: UX Designer, Engineering Manager, Domain Experts
- Informed: CPO, Stakeholder Groups, Customer Success
Technical Architecture
- Responsible: Engineering Manager, Tech Lead
- Accountable: CTO or VP Engineering
- Consulted: Product Owner, Business Analyst
- Informed: Product Director, Operations
Compliance Features
- Responsible: Product Owner, Business Analyst
- Accountable: Product Director
- Consulted: Head of Compliance, Legal, Domain Experts
- Informed: CPO, Operations, Customer Success
Contact Patterns
For PRD Review
- Product Owner (Accountable)
- Product Director (Informed)
- Engineering Manager (Consulted)
- UX Designer (Consulted)
- Relevant Stakeholders (Informed)
For Epic Kickoff
- Product Owner (leads)
- Business Analyst (supports)
- Engineering Manager + Team (delivers)
- UX Designer (designs)
For Go/No-Go Decisions
- Product Director or CPO (decides)
- Product Owner (recommends)
- Engineering Manager (technical feasibility)
- Head of Compliance (regulatory approval)
- Operations (operational readiness)
Notes
- Update Frequency: Refresh this document quarterly or when org changes occur
- Data Source: Use Employment Hero tools to sync automatically
- Privacy: This is an internal document - do not commit names/emails to public repos
- Jira Integration: Map names to Jira usernames for automatic assignment
Related Documents
- Departments & Stakeholders
- RACI Template
- Employment Hero Tools: .claude/tools/employmenthero/
To populate this document, run:
# 1. Search for senior managementnode .claude/tools/employmenthero/search-employees.cjs --senior
# 2. Search for product teamnode .claude/tools/employmenthero/search-employees.cjs --department "Product"
# 3. Update this file with actual names and emails